Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

gsm_required_manager table — gsmrm

This table contains a list of the Progress Dynamics managers that must be started during the startup of the session and the order in which they must be started. Any manager types that need to be written to the configuration file must be started first.

Table 13–13 lists the table’s FLA, fields, and foreign keys.

Table 13–13: gsm_required_manager table information 

Table FLA	Fields (data type)	Foreign keys
gsmrm	required_manager_obj (Decimal) session_type_obj (Decimal) startup_order (Integer) manager_type_obj (Decimal) object_obj (Decimal) system_owned (Logical)	manager_type_obj session_type_obj startup_order

Table 13–14 gives details of the table’s indexes.

Table 13–14: gsm_required_manager index information 

Index name	Elements	Type
XPKgsm_required_manager	required_manager_obj	Primary Unique
XAK1gsm_required_manager	session_type_obj startup_order	Unique
XAK2gsm_required_manager	manager_type_obj session_type_obj	Unique

The write_to_config attribute of the manager causes this procedure name to be written to the icfconfig.xml file. This allows the framework to start it before the session makes a connection to the run-time Repository.

The Progress Dynamics framework supports a standard set of managers that are required. Specific applications might require the startup of additional managers for performance reasons. For example, a financial system might require a frequently referenced financial manager API to be prestarted.